WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Query in relation to Web Page order when you cannot see the page.

for

From: Birkir R. Gunnarsson
Date: Oct 18, 2015 5:29PM

Make sure your page content is organized in a logical manner, such as
"header" "main" and "footer".
Make sure that this organization makes sense based on content order
alone (i.e. with CSS turned off)

Try to keep header and footer content consistent between webpages on
the same website, so that it becomes predictable and users can quickly
familiarize themselves with it on one page, use it on other pages.
Make sure the main content of the page represents the role of that
particular page.

Use ARIA landmark as well as clear visual presentation to distinguish
these different parts of your webpage.
You can further use landmarks, sections and other mechanisms to
categorize unique sections of your webpages, such as the search and
navigation links.
Make sure not to over-use that technique since the value of having
sections goes down when you ahv too many of them.
I personally would say never use more than 10 sections per page, think
more along the lines of 5 (this includes header, main and footer).
There is no WCAG rule about this, this is from a user perspective.
Along with sections and landmarks, use headings to layout the
hierarchy of your content.
When you got all these things right, you have a pretty durn good
webpage that should be clear and navigable by a large group of diverse
users.
I am not going into the other things such as clear color contrast,
good labeling, keeping labels visually located close to the form
fields they belong with. All of these things are essential, but are
not directly related to your question.
-B


On 10/17/15, Joseph Sherman < <EMAIL REMOVED> > wrote:
> Maybe compare what you hear when using tab vs using down arrow to navigate
> the page.
>
> Joseph
> On Oct 17, 2015 8:37 PM, Sean Murphy < <EMAIL REMOVED> > wrote:
> Cliff,
>
> Your point is valuable and isn't really the main thrust of my question I
> raised. I should have phrased it better. The focus is for someone who cannot
> see and is performing the accessibility testing. EG: Me.
>
> As I do not know the visual layout, how do you validate that the tab order
> as you move through the page isn't starting at the top left hand corner,
> then jumps to the middle of the page and then jumps to the right top hand
> corner? My assistive technology might treat it in a sequential order.
>
> Sean
>
>
>
>
>
>> On 17 Oct 2015, at 11:18 pm, Cliff Tyllick < <EMAIL REMOVED> > wrote:
>>
>> Sean, it's important to keep in mind that we need our Web content to be
>> accessible to everybody—not just to people who are blind, and not just to
>> people who have a single disability.
>>
>> Imagine the person who must use keyboard navigation with screen
>> magnification. Will they be able to find the spot that has focus after
>> focus has moved outside their magnified view?
>>
>> The tab order must make sense to them, too.
>>
>> Cliff Tyllick
>> Texas Department of Assistive and Rehabilitative Services
>>
>> Sent from my iPhone
>> Although its spellcheck often saves me, all goofs in sent messages are its
>> fault.
>>
>>> On Oct 16, 2015, at 12:19 PM, Cousins, Earl < <EMAIL REMOVED> >
>>> wrote:
>>>
>>> Hi Sean,
>>>
>>> One of the ways you can check reading order is by disabling CSS on the
>>> page (via various developer plugins etc.) and checking if the resulting
>>> list of elements are in a logical and intended order. This would be the
>>> default order that elements would accept focus (visual keyboard users)
>>> and in which screen readers would announce the content.
>>>
>>> Hope this helps!
>>>
>>>
>>> Earl Cousins | Accessibility Technical Analyst
>>> >>>
>>>