Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
Capture the sidebar grouping candidates and add a mobile-drawer pa11y run
Twenty-three shots in toc-ux-shots/: the status quo, the responsive treatment
and the collapsed treatment, at 1440x900 and 390x844, in both themes and both
languages, plus the tapped and keyboard-focused states of the fold control.
Desktop shots are clipped to the sidebar column, which is the subject; phone
shots are the whole viewport, because there the tree is a drawer over the page.
The pa11y config for the drawer opens the hamburger before testing, which the
default run never does, so the folded tree and its controls are audited in the
state a phone reader actually sees.
The fold control keeps a 40px square target on the drawer, past the 24px floor
of WCAG 2.2 SC 2.5.8 and small enough that the eleven closed groups still fit
one screen, and it restates the two eyebrow-header rules that the row wrapper
would otherwise stop matching.
