- Issue created by @rkoller
- π¨π¦Canada SKAUGHT
@rkoller
#1 "In regards of the navigation logo announce that logo link is forwarding the user to the front page of the default theme."- using hidden text in the A tag
- using title text in A Tag
- what phrase should be used.extending
- Navigation config for phrase
- wide: Navigation config for Path itself? - π¨π¦Canada SKAUGHT
Have opened π navigation Logo does not communicated where the link is taking the user Needs work after discussing in admin_ui meeting to start breaking off these items.
- π©πͺGermany rkoller NΓΌrnberg, Germany
re #4 π Make the link descriptions more descriptive, helpful, and clear. Active I've commented on the newly created issue. and a good call tagging it for usability review. even though it is a short label for the logo, it is kind og tricky and it might be beneficial discussing it in a group context
the only question i have what do you mean with
extending
- Navigation config for phrase
- wide: Navigation config for Path itself?could you clarify that please?
- π¨π¦Canada SKAUGHT
I had asked ckrina (in admin_ui meeting this morning) about this comment. i put it here to be able to discuss for the actual followup ticket summary.
I was proposing around if we need the fields on the form (: - Status changed to Needs work
over 1 year ago 4:14pm 7 May 2024 - πͺπΈSpain ckrina Barcelona
Thanks @rkoller for the feedback!
Removing "In regards of the navigation logo announce that logo link is forwarding the user to the front page of the default theme." since it has its own issue in π navigation Logo does not communicated where the link is taking the user Needs work .
Also, this issue should be split into smaller issues with specific recommendations for each point so they can be addressed easier. Smaller and focused issues are always better and easier. :) - πΊπΈUnited States kentr Durango, CO
Uncertain if this is in scope or warrants a separate issue.
In π Use ARIA disclosure pattern for submenu buttons in vertical toolbar orientation Needs work , the recommendation was to remove "Extend" and "Collapse" from the accessible names of menu toggle buttons.
This is also relevant to the Navigation toggle buttons. For example, the accessible name of the "Shortcuts" menu item toggles between "Extend Shortcuts" and "Collapse Shortcuts".
From π Use ARIA disclosure pattern for submenu buttons in vertical toolbar orientation Needs work :
@andrewmacpherson (issue summary):
Currently these buttons conflate the name and state; the name of the button is the opposite of the current state. There's some unnecessary cognitive effort there, to figure out what the current state is. (This is the standard challenge with labeling a toggle control.)
@cwilcox808 ( #35 π Use ARIA disclosure pattern for submenu buttons in vertical toolbar orientation Needs work ):
Using the aria-expanded state instead of words like Extend/Collapse in the button name is definitely the right thing to do.