> Elements with attribute aria-activedescendant should have tabindex value
> An element with an aria-activedescendant attribute should have a tabindex value
## a11y_aria_attributes
> <%name%> should not have aria-* attributes
> `<%name%>` should not have aria-* attributes
## a11y_autocomplete_valid
> The value '%value%' is not supported by the attribute 'autocomplete' on element <inputtype="%type%">
> '%value%' is an invalid value for 'autocomplete' on `<input type="%type%">`
## a11y_autofocus
@ -20,11 +20,11 @@
## a11y_click_events_have_key_events
> Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <buttontype="button"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.
> Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type="button">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.
## a11y_distracting_elements
> Avoid <%name%> elements
> Avoid `<%name%>` elements
## a11y_figcaption_index
@ -36,11 +36,11 @@
## a11y_hidden
> <%name%> element should not be hidden
> `<%name%>` element should not be hidden
## a11y_img_redundant_alt
> Screenreaders already announce <img> elements as an image.
> Screenreaders already announce `<img>` elements as an image.
## a11y_incorrect_aria_attribute_type
@ -88,23 +88,23 @@
## a11y_media_has_caption
> <video> elements must have a <trackkind="captions">
> `<video>` elements must have a `<track kind="captions">`
## a11y_misplaced_role
> <%name%> should not have role attribute
> `<%name%>` should not have role attribute
## a11y_misplaced_scope
> The scope attribute should only be used with <th> elements
> The scope attribute should only be used with `<th>` elements
## a11y_missing_attribute
> <%name%> element should have %article% %sequence% attribute
> `<%name%>` element should have %article% %sequence% attribute
w(node,"a11y_autocomplete_valid",`The value '${value}' is not supported by the attribute 'autocomplete' on element <input type="${type}">`);
w(node,"a11y_autocomplete_valid",`'${value}' is an invalid value for 'autocomplete' on \`<input type="${type}">\``);
}
/**
@ -84,20 +84,20 @@ export function a11y_autofocus(node) {
}
/**
*Visible,non-interactiveelementswithaclickeventmustbeaccompaniedbyakeyboardeventhandler.Considerwhetheraninteractiveelementsuchas<buttontype="button">or<a>mightbemoreappropriate.Seehttps://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.
*Visible,non-interactiveelementswithaclickeventmustbeaccompaniedbyakeyboardeventhandler.Considerwhetheraninteractiveelementsuchas`<button type="button">`or`<a>`mightbemoreappropriate.Seehttps://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.
w(node,"a11y_click_events_have_key_events","Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.");
w(node,"a11y_click_events_have_key_events","Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.");
w(node,"a11y_no_noninteractive_element_interactions",`Non-interactive element <${element}> should not be assigned mouse or keyboard event listeners.`);
w(node,"a11y_no_noninteractive_element_interactions",`Non-interactive element \`<${element}>\` should not be assigned mouse or keyboard event listeners.`);
w(node,"a11y_role_supports_aria_props_implicit",`The attribute '${attribute}' is not supported by the role '${role}'. This role is implicit on the element <${name}>`);
w(node,"a11y_role_supports_aria_props_implicit",`The attribute '${attribute}' is not supported by the role '${role}'. This role is implicit on the element \`<${name}>\``);
}
/**
@ -529,20 +529,20 @@ export function reactive_declaration_module_script(node) {
w(node,"store_rune_conflict",`It looks like you're using the \`$${name}\` rune, but there is a local binding called \`${name}\`. Referencing a local variable with a \`$\` prefix will create a store subscription. Please rename \`${name}\` to avoid the ambiguity`);
exportfunctionstate_referenced_locally(node){
w(node,"state_referenced_locally","State referenced in its own scope will never update. Did you mean to reference it inside a closure?");
w(node,"state_referenced_locally","State referenced in its own scope will never update. Did you mean to reference it inside a closure?");
exportfunctionstore_rune_conflict(node,name){
w(node,"store_rune_conflict",`It looks like you're using the \`$${name}\` rune, but there is a local binding called \`${name}\`. Referencing a local variable with a \`$\` prefix will create a store subscription. Please rename \`${name}\` to avoid the ambiguity`);
}
/**
@ -589,6 +589,15 @@ export function attribute_invalid_property_name(node, wrong, right) {
w(node,"attribute_invalid_property_name",`'${wrong}' is not a valid HTML attribute. Did you mean '${right}'?`);
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"start":{
"line":13,
"column":0
@ -13,7 +13,7 @@
},
{
"code":"a11y_click_events_have_key_events",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"start":{
"line":15,
"column":0
@ -25,7 +25,7 @@
},
{
"code":"a11y_click_events_have_key_events",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"start":{
"line":18,
"column":0
@ -37,7 +37,7 @@
},
{
"code":"a11y_click_events_have_key_events",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"start":{
"line":20,
"column":0
@ -49,7 +49,7 @@
},
{
"code":"a11y_click_events_have_key_events",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"start":{
"line":22,
"column":0
@ -61,7 +61,7 @@
},
{
"code":"a11y_click_events_have_key_events",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"start":{
"line":24,
"column":0
@ -73,7 +73,7 @@
},
{
"code":"a11y_click_events_have_key_events",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"start":{
"line":26,
"column":0
@ -85,7 +85,7 @@
},
{
"code":"a11y_click_events_have_key_events",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as <button type=\"button\"> or <a> might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message":"Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",