Which of the following ways to incorporate SVGs are considered bad for accessibility?

Using the <object> element to incorporate SVGs is often considered a poor choice for accessibility due to its inherent complexities and limitations in how it handles content. When SVGs are embedded using <object>, they may not be accessible to users with assistive technologies such as screen readers. This is primarily because the content inside the object may not be interpreted correctly, leading to a lack of proper semantic information.

In contrast, the other methods of incorporating SVGs—using <svg>, <img>, or <iframe>—are generally more accessible. The <svg> element allows for direct manipulation of the SVG markup, providing better control over accessibility features and ensuring that assistive technologies can interpret the content correctly. The <img> element has attributes such as alt text that directly enhance accessibility. While <iframe> can introduce some challenges, accessibility can still be managed effectively with proper titles and roles.

Therefore, utilizing the <object> tag for SVGs tends to complicate accessibility efforts and is less favorable compared to the other methods mentioned.