agaric/agaric-coop
10
1
Fork 0
Code Issues 102 Pull requests Projects Releases Packages Wiki Activity

Review accessibility of our listless menus #77

New issue
Open
opened 2018-08-24 13:24:14 +00:00 by mlncn · 3 comments
mlncn commented 2018-08-24 13:24:14 +00:00 (Migrated from gitlab.com)
Copy link

Following the lovely design's static layout perhaps a bit too closely, i implemented it as shown with <div>s rather than <ul>s and unadorned <a> instead of <li> tags. This didn't concern me at all from an accessibility perspective until getting to the sub-menus— this, it seems, should have a semantic way of being 'below' their parent items in the hierarchy.

My implementation: https://gitlab.com/agaric/patternlibrary/blob/master/agaric/templates/navigation/menu.html.twig

Original: https://cgit.drupalcode.org/bulma/tree/templates/navigation/menu.html.twig

Following the lovely design's [static layout](https://gitlab.com/agaric/patternlibrary/blob/master/static-layouts/design-output/index.html) perhaps a bit too closely, i implemented it as shown with `<div>`s rather than `<ul>`s and unadorned `<a>` instead of `<li>` tags. This didn't concern me at all from an accessibility perspective until getting to the sub-menus— this, it seems, should have a semantic way of being 'below' their parent items in the hierarchy. My implementation: https://gitlab.com/agaric/patternlibrary/blob/master/agaric/templates/navigation/menu.html.twig Original: https://cgit.drupalcode.org/bulma/tree/templates/navigation/menu.html.twig
mlncn commented 2018-08-24 13:31:17 +00:00 (Migrated from gitlab.com)
Copy link

mentioned in commit agaric/patternlibrary@d91434b9b6

mentioned in commit agaric/patternlibrary@d91434b9b6786ee3388f4d9bfa684fd922911efd
mlncn commented 2018-08-24 13:34:22 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
mlncn commented 2022-03-11 19:21:00 +00:00 (Migrated from gitlab.com)
Copy link

My instinct is probably correct, there's not much reason for unordered lists for menu accessibility in general, mixed results with screenreaders, but i'd be interested in an accessible UX look at menu hierarchies in particular.

My instinct is probably correct, there's not much reason for unordered lists for menu accessibility in general, mixed results with screenreaders, but i'd be interested in an accessible UX look at menu hierarchies in particular.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
bbb-test
D9-upgrade
drush-9-aliases
provision-dewey
No results found.
Labels
Clear labels   
A11y

Accessibility-related issues

  
Automated Testing

   
Contributable

Issues with work that can (potentially) be contributed back to Drupal or other FLOSS projects.

  
Contributed

Tag issues where we have contributed work back to FLOSS projects (replace Contributable tag; the Contributed tag can be removed once the contribution is recorded in a blog or something.

  
Decision

An issue that requires a decision be made.

  
Design

Issues that should include a UX/design work or review.

  
Development

   
Drutopia

Issues related to Drutopia features or infrastructure, or are potential Drutopia enhancements (with tag Contributable).

  
Feature Request

   
IndieWeb

Anything related to interlinking web sites in a broadly IndieWeb fashion, see https://indieweb.org/

  
Infrastructure

   
Marketing

   
Needs documentation

When an issue has uncovered something that should be documented in a user guide or the project wiki or anywhere else outside the issue queue.

  
status::Abandoned

An issue that has been abandoned and will not be completed.

  
status::Blocked

An issue that is blocked for a reason outside Agaric's control.

  
status::Deploy

An issue that has been tested and is ready to be deployed.

  
status::Doing

   
status::Done

   
status::In Review

An issue that has been completed and is ready for a code and/or design review.

  
status::Needs Clarification

   
status::Test

An issue that has been completed and is ready to be tested.

  
status::To Do

An issue that is an agreed priority and has all information needed to be completed.

  
type::Bug

   
type::Task

   
type::User Story
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
Feature Request
IndieWeb
Infrastructure
Marketing
Needs documentation
status::Abandoned
status::Blocked
status::Deploy
status::Doing
status::Done
status::In Review
status::Needs Clarification
status::Test
status::To Do
type::Bug
type::Task
type::User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: agaric/agaric-coop#77
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?