accessibility | add accessibility to your website | HTTP library

Apple often seems to inadvertently break testing tools, especially the Test Recorder and Accessibility Inspector. I'd suggest you use an older version of Xcode until you have a strong need to upgrade. These can be downloaded from Apple's More Downloads page.

If you wish to retain 13.3 I'd suggest renaming it to Xcode_13_3.app prior to installing a prior version, which will install as Xcode.app.

I also highly advise against using the App Store to keep your Xcode up to date (if that's what you're doing). Instead manually download new versions via the link above and rename old versions (in case you find broken things in the new one) also as described above.

The following only deals with the first of the errors you mention (as this one is pretty clear thanks to @BenBolkers comment), but hopefully it points you to the right tools to use.

I'd use htmltools::tagQuery to make the needed modifications - please check the following:

Which method(s) are best for users?

Method 1 out of the options given is best.

Which method(s), if any, would NOT satisfy WCAG Level AA and therefor not comply with laws in the US, EU, etc.

None of them would fail WCAG as such.

However as you have pointed out 2 and 3 result in duplication of effort for keyboard users and links to the same location having different names, which is not a fail under any success criterion but is highly recommended.

Would the image in a Product Listing Page be classified as "decorative"?

Yes in scenario 1 and 4.

Expansion of the answers given

All 4 of the examples given would "pass" WCAG. However they offer very different experiences.

So the question is what things are we considering for accessibility?

The first is Keyboard operability. Examples 2 and 3, as you pointed out result in duplication of focus stops for the same item. So we should avoid them.

The second thing is link purpose. Yet again examples 2 and 3 are not great here as we have 2 links to the same place on the same page that have different accessible labels / text that assistive tech will use.

So we can rule out options 2 and 3 for best practices.

So what about options 1 and 4?

Well as the items are located within a hyperlink we want the link text (the accessible name for those links) to be descriptive of the product page we are going to visit.

As such option one would read: "link: Squeaky Fox Dog Toy" and the second link would read "link: (image) Red fox stuffed dog toy with white braided rope arms, Squeaky Fox Dog Toy"

The second option results in duplication of information so is not as desirable as the first option.

So we land on option 1.

The only consideration you now have is whether that link text describes the product sufficiently. Now if you sold multiple dog toys (different product types) then you need text that describes them as such i.e. "plastic dog toys" and "fluffy dog toys".

If you sell different coloured products and they all had their own page (so you don't have a colour picker on the end page, they are listed as separate items) then you would need to describe the colour there too. "Red fluffy dog toy", "blue fluffy dog toy".

Essentially you need to provide enough information that each product link is easily identifiable as to where it leads (the purpose of the link itself).

This is where judgement comes into play, provide enough information to describe the product generally in a unique way on the page, not so much information that browsing that page becomes problematic due to 100 products with 200 word link text.

So in the example given the "balance" would be something like "Red fox stuffed dog toy", and then describe the appearance in far more detail on the product page, wither in the description or in the product image alt attributes.

Option 5 - if you don't have text at all.

It is worth noting that the last option for a product page is no text at all. Just an image inside a link. The following is also valid HTML and accessible as the alt text will be used as the link text (not if an image contains any text at all that should all appear in the alt attribute).

As @CommonsWare correctly pointed out, you need to reverse scaling.

You can get fontScale from LocalDensity:

This is no longer an issue for me. It looks like one of the Xcode or iOS updates took care of it. Not sure which.

Okay after having a discussion with 3rd party lib, they updated lib to ask for accessibility permission and we added proper consent and permission disclosure screens in the app, and it worked !!

The "member interpretation" refers to begin_expr and end_expr using members of the iterated type in contrast to using plain offsets for arrays or begin and end free functions.

The array interpretation is off the table, because it is only used for arrays. Next consider that there is std::begin and std::end:

Custom overloads of begin may be provided for classes and enumerations that do not expose a suitable begin() member function, yet can be iterated.

Now consider this example:

Okay, so I have figured it out after asking this question on swig github repository. Following answer courtesy to William Fulton:

SWIGTYPE_xxx classes are called Type Wrapper Classes.

You need to use the C type for the typemap that causes the type wrapper class to be generated. For example SWIGTYPE_p_int is wrapping an int *. Hence you'd use:

%typemap(csclassmodifiers) int * "internal class"

The defaults for all generated proxy and type wrapper classes comes from csharp.swg:

%typemap(csclassmodifiers) SWIGTYPE, SWIGTYPE *, SWIGTYPE &, SWIGTYPE &&, SWIGTYPE [], SWIGTYPE (CLASS::*) "public class"

So just override these typemaps to provide your customised code and read the chapter on Typemaps in the documentation.

As you can see in strace, the execve command executes as: execve("/bin//nc", ["/bin//nc", "/bin//nc-e //bin/bash -nvlp 4455"], NULL) = 0 It seems to be taking the whole /bin//nc-e //bin/bash -nvlp 4455 as a single argument and thus thinks it's a hostname. In order to get around that, the three argv[] needed for execve() is pushed seperately. argv[]=["/bin/nc", "-e/bin/bash", "-nvlp4455"] These arguments are each pushed into edx, ecx, and ebx. since ebx needs to be /bin/nc, which was already done in the original code. we just needed to push 2nd and 3rd argv[] into ecx and edx and push it into stack. After that we just copy the whole stack into ecx, and then xor edx,edx to set edx as NULL.

Here is the correct solution: