WebAIM - Web Accessibility In Mind

E-mail List Archives

Dynamic page query

for

From: mhysnm1964
Date: Jul 4, 2018 2:36AM

All,



If a web site is a single page (dynamic) design. I have a couple of
questions on WCAG SC failures.

1. If there is an link that is used to expand and collapse parts of
the page. The Screen reader does not get reported the current state of the
link. I assume SC 4.1.2 applies here. Any others?

2. Should the focus move to the first shown interactive element or stay
on the link which you have just activated to expand to reveal the extra
options? Failure on what SC?
3. If a normal link updates the page, should the focus move to the
beginning of the new content? If this is correct, what SC failure?
4. 4. Tables, the header row does this have to be the first column or
can it be defined to make the contextual understanding of where the screen
reader user is currently in the table to make more sense. For example, the
first column might have the same information in each cell while the 2nd
column has more meaningful information.
5. Is it a requirement to notify the user the current link will open in
a new tab or window? If so, again which SC?
6. Now for the biggie. Title of page. The current implementation I find
very nice in this web site I am looking at. If you are in a section of the
page. The title of the page is announced then the current header section.
For example "Sample page Heading 2 test equipment". If you are located in a
different part of the page the last part of the title changes. This has been
tested with Jaws using the insert+t command for title of window. Thus far so
good. The challenge is when a new page is open with the same beginning title
""Sample page" and the same method is used for the new page. This brings an
issue of the user knowing which tab or window they are in. I feel this
becomes a failure of title page. Thoughts?

Sean