NerdeFocus
Quickly debug focus problems when testing a page for accessibility issues.
Total ratings
4.43
(Rating count:
7)User reviews
Recent rating average:
4.50
All time rating average:
4.43
Rating filters
5 star 4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2023-11-30 |  | | en | Thanks, works for me (Brave v1.60.118) |
| 2023-11-28 |  | | en | Doesn't work. |
| 2023-09-04 |  | | Fantastic! | |
| 2023-09-04 |  | | en | Fantastic! |
| 2021-03-19 | Peter Eastman | | This worked great for me after a restart of the browser. | |
| 2021-03-19 |  | | en | This worked great for me after a restart of the browser. |
| 2019-03-19 |  | | This is a brilliant extension! I use it daily in my work as an accessibility consultant. If I can wish for a new feature, I would like to have more information about each focused element in the log. For instance, you could present the accessible name of the focused element together with the CSS path. That would make it a little bit easier to distinguish exactly which element it is. You should also make it possible to right click the logged element to view it in the DOM inspector. | |
| 2019-03-19 |  | | en | This is a brilliant extension! I use it daily in my work as an accessibility consultant. If I can wish for a new feature, I would like to have more information about each focused element in the log. For instance, you could present the accessible name of the focused element together with the CSS path. That would make it a little bit easier to distinguish exactly which element it is. You should also make it possible to right click the logged element to view it in the DOM inspector. |
| 2018-07-02 |  | | I loved the idea, didn't work form me. :( Chrome Version 67.0.3396.87 (Official Build) (64-bit) Ubuntu 18.04 LTS | |
| 2018-07-02 |  | | en | I loved the idea, didn't work form me. :( Chrome Version 67.0.3396.87 (Official Build) (64-bit) Ubuntu 18.04 LTS |