E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 2 (In chronological order)

From: Sarah Ferguson
Date: Tue, Apr 11 2017 2:11PM
Subject: form not presenting ideally with CSS disabled
No previous message | Next message →

Hello all,

I'm giving feedback on a webpage with an embedded form. With CSS disabled,
most of the page is fine: all the content seems to be there, the order is
clear. However, 2 things jump out at me.

1) Some parts of the page are randomly centered or right aligned (the rest
of the page is left aligned). It's still *usable*, but it looks awkward and
it makes it a little harder to read.

2) After the postal code field, there is a bunch of gibberish (possibly
code to check if the zip code is legit). Again, the field is usable, but
would it be concerning to a user? I find it very distracting. I tested it
with Voiceover: with CSS on, the gibberish does not read, with CSS
disabled, the gibberish *does* read.

My question is, do I call these things out as errors? They are obviously
not ideal, but I can't find anything to back up why they *must* be fixed.

Thoughts?

Thanks,
Sarah

--
Sarah Ferguson
Web Accessibility Specialist
Department of Digital Communications
Brandeis University

From: Jonathan Avila
Date: Tue, Apr 11 2017 2:16PM
Subject: Re: form not presenting ideally with CSS disabled
← Previous message | No next message

> I'm giving feedback on a webpage with an embedded form. With CSS disabled, most of the page is fine: all the content seems to be there, the order is clear. However, 2 things jump out at me.

WCAG 2 A/AA does not require that a page be usable with CSS disabled if you are making a claim that CSS is used in a accessibility supported way. It sounds like it likely is being used an accessibility supported way. To confirm you would need to make sure that hidden information is not seen by screen readers and other AT in the user agents (browsers) that you are claiming as the technology stack for conformance.

The current Section 508 does indicated that a page be readable without an associated stylesheet -- however, some but not all agencies interpret that older requirement that way.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group 
= EMAIL ADDRESS REMOVED =
703.637.8957 (Office)

Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Download our CSUN Presentations Here!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sarah Ferguson
Sent: Tuesday, April 11, 2017 4:12 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] form not presenting ideally with CSS disabled

Hello all,

I'm giving feedback on a webpage with an embedded form. With CSS disabled, most of the page is fine: all the content seems to be there, the order is clear. However, 2 things jump out at me.

1) Some parts of the page are randomly centered or right aligned (the rest of the page is left aligned). It's still *usable*, but it looks awkward and it makes it a little harder to read.

2) After the postal code field, there is a bunch of gibberish (possibly code to check if the zip code is legit). Again, the field is usable, but would it be concerning to a user? I find it very distracting. I tested it with Voiceover: with CSS on, the gibberish does not read, with CSS disabled, the gibberish *does* read.

My question is, do I call these things out as errors? They are obviously not ideal, but I can't find anything to back up why they *must* be fixed.

Thoughts?

Thanks,
Sarah

--
Sarah Ferguson
Web Accessibility Specialist
Department of Digital Communications
Brandeis University