question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug Report] v-select aria-readonly attr is false on input element but should be true

See original GitHub issue

Environment

Vuetify Version: 2.4.2 Vue Version: 2.6.10 Browsers: Chrome 87.0.4280.141 OS: Windows 10

Steps to reproduce

check html result input element

Expected Behavior

<input id="input-3" readonly="readonly" type="text" aria-readonly="true" autocomplete="off">

Actual Behavior

<input id="input-3" readonly="readonly" type="text" aria-readonly="false" autocomplete="off">

Reproduction Link

https://codepen.io/chrmorqmatic/pen/jOMdaLa

Other comments

This should be consistent, both value should be the same, in the v-select sourcecode, readonly is always true on the input element but the aria-readonly comes from this.isReadonly that doesn’t exists and thus is aways false.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
chrmorqmaticcommented, Jan 19, 2021

We’ll check the screen readers and keep you informed

We have tested this issue with NVDA and chrome and it works fine, so let’s close this issue

1reaction
chrmorqmaticcommented, Jan 18, 2021

Does this cause problems in screen readers?

Yes, we received the report from a customer auditing our application for WCAG accessibility, here it is:

This has a mismatch between the value of its readonly and aria-readonly attributes When ARIA attributes (state, roles, and properties) are not used correctly assistive technology may not correctly function as expected. Valid markup should always be used. Developers must use valid markup and follow the rules of the ARIA specification.

It’s inherited from v-text-field, set the readonly prop and you’ll see it change.

adding readonly prop makes the v-select readonly and cannot be edited. A value cannot be selected.

Read more comments on GitHub >

github_iconTop Results From Across the Web

aria-readonly - Accessibility - MDN Web Docs
The aria-readonly attribute indicates that the element is not editable, but is otherwise operable.
Read more >
how to set aria-readonly to false for a table using jquery? i ...
i think aria-readonly atrribute of table is preventing me to wrap the td in document.ready function. <table class="yui3-calendar-grid" id=" ...
Read more >
The “aria-hidden” attribute must not be specified on an “input ...
Guide describing the HTML issue detected by the W3C Validator: The “aria-hidden” attribute must not be specified on an “input” element whose “type” ......
Read more >
What you need to know about ARIA and how to fix common ...
Incorrect ARIA can actually cause more accessibility issues. Learn what else everyone ... But, the aria-label attribute renames the element.
Read more >
Tagify: No Custom dynamic attribute disables input entirely
In addition to my other Tagify app dynamic attribute bug report, ... the condition is false, it will disable the entire text input...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found