-
Notifications
You must be signed in to change notification settings - Fork 128
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
Discussion - Design pattern to identify and have a consistent navigation for a set of related pages about a common task #1627
Comments
My proposal consist in:
For example:
This proposal are major, which will break existing implementation of GCWeb. |
Comment received by email
|
The discussion from the HTML specification about the outline algorithm is still unresolved, see: whatwg/html#83 Also, we would need to have a solution that support work for browsers as determined by the wet-boew design decision #2 Which currently include Firefox, Chrome, Safari, Edge and IE11 |
Our TBS-CRA usability research was with phone users for Canada Child Benefit (16 participants). The design was successful in that people clearly understood their context, and were able to see more on their phone page than with the current very long large H1s in a service initiation page. Based on that success, we tried the new design with desktop users in a study this month with 18 public servants. An example of that prototype is here: https://tbs-proto1.openplus.ca/en/landing/report-overpayment I will leave the technical discussion to @delisma with gratitude. |
FYI - Still in progress |
@duboisp Est-ce que cet issue peut être fermé? |
Hi,
This is to open up a discussion about to develop and have a consensus on a design pattern to identify and have a consistent navigation for a set of related pages (sub-section) about a common task
The original propose solution require to use of two (2) heading level 1 (h1) and there is some technical concern about a such pattern.
Context:
CRA in collaboration with TBS have done a optimization project to improve the service initiation template. They have chosen to improve the Child Benefit pages.
Discussion goal:
The goal of this discussion is to define an HTML pattern that are going to be recognized as valid by other web accessibility expert and will work for users accessing that content with an assistive technology.
This discussion would assume the visual and the interaction pattern for mobile and desktop illustrated by the prototype would remain similar.
This discussion is to define how the visual and the interaction pattern can be technically articulated, coded and styled. That regardless how the prototype was originally coded or modified.
This discussion is focused on the design pattern for how a set of related pages could be named and navigated in a consistent manner. If you have other concern which is not related to this aspect, please open a new github issue.
For whatever proposed solution it must be conform to WCAG 2.1 Level AA, conform to W3C specification and be currently functional to users.
Note on the propose pattern:
I was been told that CRA has completed some usability research but they haven't published the result yet or I might simply currently don't where I can retrieve those UX research result/report.
Original proposed pattern:
Link:
Code form the generic prototype
Code from the child benefit prototype
Some formal reference to guide the discussion:
/cc @cfarquharson, @delisma, @bsouster
The text was updated successfully, but these errors were encountered: