generated from w3c/wai-resource-template
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Page update footer section: The accessible name and landmark region are not sufficiently descriptive #110
Labels
Milestone
Comments
The ARIA Authoring Practices (APG) Task Force just discussed The full IRC log of that discussion<MarkMcCarthy> TOPIC: Home page- The arialabel for the footer element is not descriptive.<jamesn> github: #110 <MarkMcCarthy> Matt_King: this is also a template issue <MarkMcCarthy> jamesn: does it really need an aria-label? <MarkMcCarthy> Matt_King: there's multiple contentinfos <MarkMcCarthy> jamesn: and they're both landmarks? <MarkMcCarthy> Matt_King: yes <MarkMcCarthy> Matt_King: page content info has last changed, updated by, etc. it COULD be complimentary, but it is content info, in my opinion <MarkMcCarthy> jamesn: i'd almost prefer a single footer with two regions inside it - two footers seems wrong <MarkMcCarthy> jongunderson: i think so too, there should be one footer, one banner, etc. if they have subsections, use regions <MarkMcCarthy> jongunderson: two contentinfos seems odd - it's against our landmark guidance, too <MarkMcCarthy> Matt_King: it says if there's multiple, label them, not sure it's broken. <MarkMcCarthy> Matt_King: it's not super easy to combine them <MarkMcCarthy> jamesn: i get that - i just don't think it's optimal <MarkMcCarthy> jongunderson: +1 <MarkMcCarthy> Matt_King: from an SR user, it's nice to know the page contentinfo has last update ddate, the site one has general info, etc <MarkMcCarthy> jongunderson: why not call it a "last updated" Region? <MarkMcCarthy> jamesn: right - you generally ignore contentinfo landmarks because they're generally useless. how often is there anything other than a site level one? if you didn't write the site, would you expect another one? <MarkMcCarthy> Matt_King: the rest of the WAI site has page contentinfo that contains last updated, by who, and acknowledgements <MarkMcCarthy> Matt_King: that info gets mixed up with really important info on our pages, like last updated and changelogs <MarkMcCarthy> jamesn: generally, this sounds like a template issue. can we punt to them? <MarkMcCarthy> Matt_King: this hyperspecific thing is a template issue <MarkMcCarthy> s/thing is/label thing is <MarkMcCarthy> Matt_King: i'm okay with the current label, but the site label could be enhanced. we could drive it |
mcking65
changed the title
Home page- The arialabel for the footer element is not descriptive.
Home page- The aria-label for the footer element is not descriptive.
Jun 12, 2022
mcking65
changed the title
Home page- The aria-label for the footer element is not descriptive.
Page update footer section: The accessible name and landmark region are not sufficiently descriptive
Jun 12, 2022
Net of feedback after task force discussion:
|
After examination, this is governed by the template. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The aria-label for the footer element is not descriptive. The current aria-label is "Site"
Answer from @mcking65
Do you mean the label "Site"? Are you thinking it should be "WAI" instead of "Site"? That also is part of the
WAI site template, and would not be resolved by this PR. I do agree that a better label would be "WAI" or possibly "Web Accessibility Initiative".
The text was updated successfully, but these errors were encountered: