[dialog] 'X' icon buttons are missing labels
Categories
(Firefox :: New Tab Page, defect)
Tracking
()
People
(Reporter: nstroud, Assigned: mekaranyadav8, Mentored, NeedInfo)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(2 files)
STR:
- Open Firefox Nightly
- Go to
about:newtab - In the shortcuts row, click the 'Add shortcut' button
- The 'New Shortcut' dialog will appear. Type some text in the URL text field
- Open 'Web Developer Tools' (press Ctrl + Shift + I or open the hamburger menu at the top right, More tools > Web Developer Tools)
- In dev tools, click the Accessibility tab.
- Click the 'Pick accessible object from page' icon button to the left of 'Inspector'.
- Hover over the 'X' icon button. A tooltip will appear showing that the button is missing a label
Actual / Expected:
At this time, the screenreader says 'button'
The 'X' icon button needs a label so screenreader users know its purpose. aria-label can be added to icon buttons to provide an accessible name
Comment 1•5 months ago
|
||
The severity field is not set for this bug.
:thecount, could you have a look please?
For more information, please visit BugBot documentation.
Updated•3 months ago
|
Comment 3•3 months ago
|
||
We could probably give this a "clear text" string that is concise and explicitly explains what the button does.
What we'd need is to create a new string in the newtab.ftl file and give it a dot props of .label and .aria-label.
To help Mozilla out with this bug, here's the steps:
-
Comment here on the bug that you want to volunteer to help.
This will tell others that you're working on the next steps. -
Download and build the Firefox source code: https://firefox-source-docs.mozilla.org/setup/index.html
- If you have any problems, please ask on the bug or reach out to the team.
- You can also read the Firefox Contributors' Quick Reference, which has answers to most development questions: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
-
Start working on this bug. Follow the steps the reporter of this bug has put in to replicate the issue. Also please refer to the idea I added above to get started on how to tackle this bug
- If you have any problems with this bug, please comment on this bug and set the needinfo flag for me.
-
Run and test your newtab changes:
- Open 2 terminal windows, both in the firefox directory:
- Window #1: Run
./mach newtab watch(this will watch for code changes) - Window #2: Run
./mach run(this will launch Firefox)
- Window #1: Run
- To reload the page with fresh code changes:
- Mac: Press Cmd+Opt+R
- Windows/Linux: Press Ctrl+Shift+R
- Check your changes for adherence to our style guidelines by using
./mach lint
- Open 2 terminal windows, both in the firefox directory:
-
Commit your changes with a proper commit message:
- Use the following format for your commit message:
Bug XXXXXX - Text explaining your fix. r=#home-newtab-reviewers- Replace XXXXXX with the bug number (found at the end of this bug's URL)
- Example: Bug 1234567 - Fix broken link in Top Sites menu. r=#home-newtab-reviewers
- Commit your changes with: git commit -am "Bug XXXXXX - Your description here. r=#home-newtab-reviewers"
- Important: Phabricator only needs one commit per bug. If you need to make additional changes after committing, use
git commit --amend --no-editto update your existing commit instead of creating a new one.
- Use the following format for your commit message:
-
Submit the patch (including an automated test, if applicable) for review. Mark me as a reviewer so I'll get an email to come look at your code.
- Getting your code reviewed: https://firefox-source-docs.mozilla.org/setup/contributing_code.html#getting-your-code-reviewed
- This is when the bug will be assigned to you.
-
After a series of reviews and changes to your patch, I'll mark it for checkin or push it to autoland. Your code will soon be shipping to Firefox users worldwide!
-
...now you get to think about what kind of bug you'd like to work on next. Let me know what you're interested in and I can help you find your next contribution.
Updated•3 months ago
|
Comment 8•2 months ago
|
||
Comment 9•2 months ago
|
||
Hey [:karan68], seems the bundle files are out of date, you'll need to rebase your branch off main:
- Checkout to
main - Run a
git pull - Checkout into your working branch
- Run a rebase --
git rebase main - Make sure to then run the bundle function:
./mach npm run bundle --prefix=browser/extensions/newtab - And then update your patch in Phabricator
| Assignee | ||
Comment 10•2 months ago
|
||
please close this , the bug is solved https://phabricator.services.mozilla.com/D282264
Comment 11•2 months ago
|
||
Hey Karan,
Just to re-iterate, we'll need to re-bundle and base your changes off the main branch before we land, so that your code changes can land safely.
You'll just need to follow the steps I outlined above and push your changes to Phabricator, and then we'll be able to land it.
Comment 12•2 months ago
|
||
Comment 13•2 months ago
|
||
| bugherder | ||
Comment 14•2 months ago
|
||
| bugherder | ||
Updated•2 months ago
|
Updated•1 month ago
|
Description
•