googlearchive / accessibility-developer-tools-extension Goto Github PK

I've installed the extension, it's enabled, but it's grayed out in the toolbar. I havent been able to figure out how to use it (and dying to play around with it).

Is this a known issue with a simple solution by chance? Mac El Capitan 10.11.4, Chrome Version 50.0.2661.102.

Hi, I was pretty sure there was an open issue for that but I could not find it again so here I am.

<input /> elements with a number or checkbox type (more types might be involved) seem to incorrectly report invalid ARIA attributes, such as aria-required.

Here is a demo: http://codepen.io/HugoGiraudel/pen/dNOzMw.

There is also a Twitter thread involving @stevefaulkner if you’re interested: https://twitter.com/HugoGiraudel/status/821378544626503680.

Within the "Text" panel of the accessibility content we get the very helpful content of what a screen reader might read. Seeing the handy "speaking-person" icon I expected to be able to click this and hear what would be read by the screen reader. Disappointed I thought it would be an excellent feature to have this icon actually toggle the enabled state of ChromeVox if the user has that extension also installed. If that seems to be over-loading this control, having a link to do so would be useful as the text content is only a part of what screen readers announce, so being able to hear what they actually announce would be useful for developers that don't normally check.

It would be great to consider to make the Accessibility Properties tab compatible with the Dark theme:

Hi there,

I really like the layout and cleanliness of the data in the audits. I just wish there was a way could export it and keep the same format. Export as HTML? Even a PDF with the bullets would be fine as well.

We're building a chrome extension where the content script creates an iframe inside of the host webpage and loads a .html file that is packaged with the extension inside of this iframe. The .html in turn has another iframe that loads content from our web server.

These iframes get created and removed based on user interaction.

Whenever the accessibility developer tools extension is also loaded on the browser, every time that our extension creates one of these iframes the time to load the iframe get progressively longer and at some point freezes the whole page. Everything works fine without the Accessibility Extension.

We've noticed two things that might help with investigation:

1. Our iframe receives a number of postMessages with data.request = 'getUri' every time it gets loaded
2. Eventually the Accessibility Extension starts throwing thousands of the following errors:
   "Cannot read property 'frameURIs' of undefined"

From @espeedg on #15:
On http://play.google.com/store, on the first request the error doesn't show up, but every subsequent refresh the error appears three times in 3 different places. This happens every time for me.

For a page with this HTML:

<input type="email" class="form-control" id="exampleInputEmail1" placeholder="Enter your email address">

... the auditor reports AX_TEXT_01: Controls and media elements should have labels. True, the element doesn't have a label property, but it does have a placeholder property, which even the help page it links to describes as 'good':

<!-- Good: Using placeholder text -->
<input placeholder="Enter your address">

I'm curious if there is a particular standard that is being drawn on to select which tests this tool will implement. WCAG? Something else?

When an element has a lot of attributes, this can make it difficult to tell which attributes need correcting (or removal).

See https://groups.google.com/forum/#!topic/accessible/EZdMSV2BlZ8 for an example with several attributes (many invalid).

Chrome Version 39.0.2171.71 (64-bit)
Mac OS X 10.9.5

Loads through all the elements on the page, then the status changes to "Running audit" but nothing happens. It's the same on every webpage I tested.

Nothing is outputted to the console log.

This tool is showing errors for elements which are inside elements with aria-hidden='true'or have this attribute themselves. For example <input aria-hidden="true" aria-activedescendant="smth"> would complain about incorrect aria-activedescendant

e.g. "#000 from style rule .foo" "#FFF from parent element $banner"

This will allow verifying that the contrast ratio value is being calculated correctly.

From discussion with @jyasskin

Does not show up in Audits with Opera 26.0.1656.24 Stable and Opera 27.0.1689.2 DEV (windows).

1. Install Download Chrome Extension for downloading from Chrome Web Store and activate extension
2. Install Accessibility Developer Tools and activate extension
3. Hit Ctrl Shift I to start Developer Tools
4. Select Audits in Developer Tools
5. Missing point Accessibility to select

No error messages found in Console of Developer Tools in Opera.

Extension works with Iron 38.0.2050.0 (295000).

Seems, Extension does not work in Chromium clone Opera 26.

Sometimes I get a bunch (thousands) of the following errors:
"Cannot read property 'frameURIs' of undefined"
"Cannot read property 'removeFragment' of undefined"

It causes the page to freeze, not possible to scroll, click links etc. I'm quite sure it's related to some ads.

It is used in the background script.

https://developer.chrome.com/extensions/extension#event-onRequest

chrome.runtime.onMessage is to be used instead.

I don't think this this is possible at the moment (I've tried all manner of keyboard shortcuts and nothing's worked).

In the color contrast tool, it would be really useful to be able to alter either the background or the foreground color to get a passing level of contrast. At the moment (I think) it's only possible to change the background color, which I find is more often than not, not the color I want to change.

I keep getting this error in the console, stemming from audits.js, even when not using Audits in dev tools.

The "goog" object doesn't contain anything, so thus it is failing when the rest of the code assumes that it has various functions registered as properties.

Seems maybe all of these lines referencing the goog object shouldn't actually be in the extension code?

Using version 2.10.9 in Chrome 48.0.2564.116 m.

@alice the extension is returning false negatives for me in Chrome Stable. Every page I've audited returns not applicable and passing results, no failures. Works in Canary.

http://www.w3.org/TR/wai-aria/states_and_properties#aria-hidden

Same for several others; aria-label, aria-disabled, etc.

Reported here: https://groups.google.com/forum/#!category-topic/introduction-to-web-accessibility/ChGzBSe0_yU

role="main" does not allow name from: contents, so getting text alternatives is the incorrect method for calculating text content.

During a course on Udacity, we should fix an issue with active element which grabs focus even if it is outside the viewport. The extension did not found it as an issue. See https://github.com/udacity/ud891/tree/gh-pages/lesson2-focus/04-offscreen-content.

(Yes, It can be fixed by adding proper css property.)

The library allows this already via the 'scope' option (https://github.com/GoogleChrome/accessibility-developer-tools/blob/master/src/js/AuditRule.js#L150); we just need a way of exposing this to the user.

One implementation idea: in the Accessibility sidebar pane, have a "set audit scope" link/button which sets that element as the scope for the audit. This would then be used as the scope until either the scope is cleared (have an always-visible button in the sidebar pane for that if a scope is set) or set to some other element. This then sets a preference in the extension prefs to always use an element with that element's unique CSS selector as the scope; while the current devtools session is running we can use a reference to the actual element instead.

When test is performed target device always turn into mobile view (Nexus 5X) even if it is removed from emulation list.
Should be possible to use for currently active mobile emulation at least.

For some reason, the accessibility properties panel is empty.

I've only had this extension installed for two days. Pretty sure this worked yesterday (I was able to see color contrast ratios in this panel for elements). Today, it's blank.

Any help is appreciated.

In my local dev environment and on preview servers locked by .htaccess I constantly receive errors in chrome devtools saying axs is not defined.

Uncaught ReferenceError: axs is not defined constants.js:1
Uncaught ReferenceError: axs is not defined utils.js:1
Uncaught ReferenceError: axs is not defined audits.js:1
Uncaught ReferenceError: axs is not defined extension_properties.js:1
Uncaught ReferenceError: axs is not defined extension_audits.js:1

Reported by @bezoerb here: GoogleChrome/accessibility-developer-tools#92
cc @Nettsentrisk @dasjestyr