WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Multiple documents in a single webpage

for

From: Birkir R. Gunnarsson
Date: Jul 14, 2018 8:36AM

I think it's fine to move focus to a document when it is displayed as
the result of activating a link or a button.
It would be bad if it is displayed as a result of changing the setting
of a component (selecting a radio button, checking a checkbox,
selecting from a dropdown etc.). You can see a lot of discussion about
this in the understanding WCAG SC 3.2.2 documentation.
You can enhance this by referencing visually hidden text on the button
that says "moves focus to the document display area".

I'd suggest to use something like role="region" and
aria-label="document" for the container element.
This is what aria-roledescription could be useful for, but so far it
has limited support and even does more harm than good (e.g. in IE it
overrides the semantics inside the document, with Jaws at least).

If you have
<div role="region" aria-roledescription="document panel"
aria-label="document name">
<h1>main heading</h1>
<p>text.</p>
<h2>Heading 2</h2>
...
</div>

an navigate to the headings inside the document, the headgs and levels
are no longer announced by Jaws, only the role description "document
panel" and the name.

Does the document region contain a button to close or move focus back
to the webpage?





On 7/13/18, glen walker < <EMAIL REMOVED> > wrote:
> I think what Sean was asking about was moving the dialog itself. Since the
> dialog can be moved by dragging it or using the move handles (nice job
> allowing that from the keyboard), how does the AT user know where the
> dialog is now?
>
> With powerpoint, which I think I mentioned in some other thread, the
> location of the object is announced as you move it around. You're also
> notified if the object moves over the top or underneath another object. Is
> anything like that announced when you move your dialog? Is the dialog
> truly "on top" of the page in the background, or does stuff reflow around
> it as you move it around? If it's on top, when it first appears, does
> anything in the background get covered up? I'm guessing as you move it,
> other stuff on the main page might get covered up?
>
>
> On Fri, Jul 13, 2018 at 7:17 AM, Isabel Holdsworth <
> <EMAIL REMOVED> > wrote:
>
>> If we didn't move the focus, screenreader users would be unlikely to
>> know that some new content had appeared. And it may be difficult for
>> them to find. If they pressed the button to open the dialog, chances
>> are they're interested in what's in there, so why not position the
>> cursor so they can begin reading at the correct place?.
>>
>> The focus should rarely be moved programatically, but I think this is
>> one of those times when it's acceptable and even advisable.
>>
>> On 13/07/2018, <EMAIL REMOVED> < <EMAIL REMOVED> > wrote:
>> > I have one question. How does the screen reader user know where they
>> > are
>> > when you move the document within the page? What is the purpose of
>> > moving
>> > the document?
>> >
>> >