Closed adamjohnson closed 5 years ago
hammer-start
The accessibility check will flag the following error:
Bypass Blocks -> No option to skip repeated content
Most of our themes (🤞) support this out of the box. This error should not exist.
The reason this is being flagged is because the Hammer Nav bar comes first in the DOM.
Output the toolbar at the bottom of the DOM, then style it so that it looks like it's at the top. Something like this:
#wvu-hammer-nav.wvu-hammer-breadcrumbs { position: absolute; top: 0; } body { padding-top: 52px; }
Note: Hammer will need some way of hooking into the <body> tag to target it (inline style? adding a class?).
<body>
Decided to solve this by just hiding the toolbar when remediating accessibility issues. Do that by adding the following to the top of your mock_data.yml file:
mock_data.yml
hammer_nav: disabled: true
Steps to reproduce the issue
hammer-start
)Results
The accessibility check will flag the following error:
Expected results
Most of our themes (🤞) support this out of the box. This error should not exist.
The reason this is being flagged is because the Hammer Nav bar comes first in the DOM.
Potential Solution
Output the toolbar at the bottom of the DOM, then style it so that it looks like it's at the top. Something like this:
Note: Hammer will need some way of hooking into the
<body>
tag to target it (inline style? adding a class?).