AndreasSamjeske

> Similar to #3424 which was [fixed](https://github.com/vaadin/web-components/pull/3450) by applying the `aria-lebel` attribute only on expandable rows. You probably mean `aria-level`. Just wanna make sure, since it can easily be taken...

Might have something to do with #6950

In our Vaadin Webapp we made all controls (inputs, select, checkbox, etc.) having a black border for a11y reasons. Sadly, the webapp is not yet Vaadin 24.1, so we didn't...

> ... > Which means that if you implement it along the lines of > > ``` > :host([focus]) { > box-shadow: 0 0 0 var(--_focus-ring-width) var(--_focus-ring-color); > } >...

Let's be clear: A URL having an "naked" % is an invalid URL. So, the questions at hand are: 1. Why is the initial request successful? 2. Shall Vaadin do...

Our Testers discovered there is a little more to this problem: Depending on Grids focus mode, the screenreader doesn't tell you any details regarding these chechboxes in the "Select All"...

One of our customers criticized these not localized texts "Select all" and "Sort by ..." in grids. Is there any timetable for this issue?

Thanx for providing some insight. Unfortunately our customer demands a solution. Is there any viable workaround, like overriding these values hard-coded on our side?

onAttach seems to fire too early: executed JS couldn't find sorter in header cells. So we came up with this: ``` String javascriptObserver = """ const observer = new MutationObserver((mutations,...

Same Problem with - Select - DatePicker - DateTimePicker - IntegerField - Checkbox (although I am unsure if this is supposed to work, since HTML doesn't define a readonly checkbox)...