-
Notifications
You must be signed in to change notification settings - Fork 86
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
feat: accessibility improvements #1694
base: develop
Are you sure you want to change the base?
Conversation
43b0ea5
to
41cc281
Compare
0dfaac4
to
49232f8
Compare
41023e4
to
913cb20
Compare
Azure Demo Servers are available: |
11 similar comments
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
3 similar comments
Azure Demo Servers are available: |
Azure Demo Servers are available: |
Azure Demo Servers are available: |
e266a26
to
54f05b6
Compare
31f038b
to
7fd6064
Compare
…relying on color alone, update underline behavior (#1694)
96e05b2
to
b0cef6e
Compare
caa690b
to
2bc3b36
Compare
Azure Demo Servers are available: |
…ools & changed share icon (#1694)
07127e6
to
4944351
Compare
4944351
to
73a064d
Compare
…ssword component and update error indicators (#1694) * Add functionality to toggle password visibility for password fields. * Replace TextInputFieldComponent with PasswordFieldComponent to provide password-specific functionality. * Update error field indicator from "x" to "!" for improved clarity and accessibility. BREAKING CHANGES: The TextInputFieldComponent is no longer used for password fields. Instead, the PasswordFieldComponent is now used, which includes functionality to toggle password visibility. Password validators are applied to each instance as needed.
This PR adds accessibility improvements.
PR Type
[x] Feature
What Is the Current Behavior?
Currently, the Intershop Progressive Web App (PWA) has accessibility issues related to color contrast, link identification, tab-focus visibility, semantic order of HTML elements, missing ARIA attributes, touch target sizes and others.
What Is the New Behavior?
The following accessibility issues are fixed:
lang
andtitle
attributesaria-label
to language switch toggle, mini-cart toggle, search input, sorting selectbox, product compare link, recently viewed link, product brand link (WCAG 2.5.3 - Label in Name & WCAG 3.3.2 - Labels or Instructions) and to star-rating on product detail page (WCAG 1.1.1 - Non-text Content)aria-haspopup
,aria-expanded
andaria-controls
to mini-cart (WCAG 4.1.2 - Name, Role, Value)aria-required
,aria-invalid
to form fields (WCAG 3.3.1 - Error Identification) andaria-describedby
to form fields with related error test and / or descriptions (WCAG 3.3.2 - Labels or Instructions, based on changes to ngx-formly/bootstrap)aria-hidden
to the "*" character of required fieldslang
attribute to each language select option in the header language switch (WCAG 3.1.2 - Language of Parts)title
attribute to buttons only when they are used as an icon (WCAG 1.1.1 - Non-text Content)role="img"
attribute from logo in the header (WCAG 4.1.2 - Name, Role, Value)<div role="main">
with<main>
element for better semantics (WCAG 2.4.1 - Bypass Blocks)<legend>
-elements to form fieldsets (WCAG 1.3.1 - Info and Relationships)Does this PR Introduce a Breaking Change?
[x] Yes
Open Issues
[ ] check changes of the wishlist feature: #1590 (esp. animated buttons on PDP and "account.wishlists.shared_wishlist.error")
[ ] check b2c favicon
Other Information
AB#97976