Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify that modal requires an accessible name #1180

Merged
merged 1 commit into from
Feb 11, 2020

Conversation

WilcoFiers
Copy link
Contributor

@WilcoFiers WilcoFiers commented Jan 29, 2020

The use of the word "label" is confusing, and dialogs require an accessible name.
That is a MUST, not a SHOULD.


Diff

The use of the word "label" is confusing, and dialogs require an accessible name.
That is a MUST, not a SHOULD.
@jnurthen
Copy link
Member

Agree. We should either make this change or remove this sentence entirely as I don't believe it adds anything over and above the accessible name required: true and name from: author.

Authoring guidance like this is better in the Authoring Practices (where this is already listed)

@carmacleod
Copy link
Contributor

carmacleod commented Jan 29, 2020

I like this change, and I would prefer that the sentence stay in the spec prose for dialog.

I agree that it doesn't specify anything over and above accessible name required: true and name from: author, however it's surprising how many authors just don't get this.

I would almost go one further and add another sentence that says,

If the dialog contains visible content that serves as a description, authors SHOULD use aria-describedby on the dialog element to point to that content.

@carmacleod
Copy link
Contributor

Come to think of it, it might even be a good idea to have a sentence pointing out aria-modal, because it is buried in the list of inherited properties and there's no indication in the prose that it just might be really important... perhaps something like:

If the dialog is modal, then authors MUST set the dialog's aria-modal to true.

@scottaohara
Copy link
Member

I'm a bit wary of those additional suggestions @carmacleod. IMO those definitely belong over in the guidance, as I can think of situations where I very well wouldn't agree to either of those.

@carmacleod
Copy link
Contributor

I can think of situations where I very well wouldn't agree to either of those.

Oh! ... what are the situations?

scottaohara
Copy link
Member

@scottaohara scottaohara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@carmacleod
Copy link
Contributor

This PR is good to go.
+1

I'll open another issue to consider adding more about aria-describedby and aria-modal to the dialog prose. :)

mcking65
Copy link
Contributor

@mcking65 mcking65 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@jnurthen jnurthen merged commit dfe62bf into w3c:master Feb 11, 2020
jnurthen pushed a commit that referenced this pull request Feb 11, 2020
The use of the word "label" is confusing, and dialogs require an accessible name.
That is a MUST, not a SHOULD.
carmacleod pushed a commit that referenced this pull request May 7, 2020
The use of the word "label" is confusing, and dialogs require an accessible name.
That is a MUST, not a SHOULD.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant