.\u00a0<\/span><\/p>\n\u201c<\/span>Effective today (June 21), new customers need to apply for access to use facial recognition operations in Azure Face API, Computer Vision, and Video Indexer. Existing customers have one year to apply and receive approval for continued access to the facial recognition services based on their provided use cases. By introducing Limited Access, we add an additional layer of scrutiny to the use and deployment of facial recognition to ensure use of these services aligns with Microsoft\u2019s Responsible AI Standard and contributes to high-value end-user and societal benefit. This includes introducing use case and customer eligibility requirements to gain access to these services. <\/span><\/p>\n“Facial detection capabilities\u2013including detecting blur, exposure, glasses, head pose, landmarks, noise, occlusion, and facial bounding box \u2014 will remain generally available and do not require an application.\u201d<\/span><\/p>\nLook at that second sentence, where Bird highlights this additional hoop for users to jump through \u201cto ensure use of these services aligns with Microsoft\u2019s Responsible AI Standard and contributes to high-value end-user and societal benefit.\u201d<\/span><\/p>\nThis certainly sounds nice, but is that truly what this change does? Or will Microsoft simply lean on it as a way to stop people from using the app where the inaccuracies are the biggest?\u00a0<\/span><\/p>\nOne of the situations Microsoft discussed involves speech recognition, where it found that \u201c<\/span>speech-to-text technology across the tech sector produced error rates for members of some Black and African American communities that were nearly double those for white users,\u201d said Natasha Crampton, Microsoft\u2019s Chief Responsible AI Officer. \u201cWe stepped back, considered the study\u2019s findings, and learned that our pre-release testing had not accounted satisfactorily for the rich diversity of speech across people with different backgrounds and from different regions.\u201d<\/span><\/p>\nAnother issue Microsoft identified is that people of all backgrounds tend to speak differently in formal versus informal settings. Really? The developers didn\u2019t know that before? I bet they did, but failed to think through the implications of not doing anything.<\/span><\/p>\nOne way to address this is to reexamine the data collection process. By its very nature, people being recorded for voice analysis are going to be a bit nervous and they are likely to speak strictly and stiffly. One way to deal with is to hold much longer recording sessions in as relaxed an environment as possible, After a few hours, some people may forget that they are being recorded and settle into casual speaking patterns.\u00a0<\/span><\/p>\nI’ve seen this play out with how people interact with voice recognition. At first, they speak slowly and tend to over-enunciate. Over time, they slowly fall into what I\u2019ll call “Star Trek” mode and speak as they would to another person.<\/span><\/p>\nA similar problem was discovered with emotion-detection efforts.\u00a0<\/span><\/p>\nMore from Bird: \u201c<\/span>In another change, we will retire facial analysis capabilities that purport to infer emotional states and identity attributes such as gender, age, smile, facial hair, hair, and makeup. We collaborated with internal and external researchers to understand the limitations and potential benefits of this technology and navigate the tradeoffs. In the case of emotion classification specifically, these efforts raised important questions about privacy, the lack of consensus on a definition of emotions and the inability to generalize the linkage between facial expression and emotional state across use cases, regions, and demographics. API access to capabilities that predict sensitive attributes also opens up a wide range of ways they can be misused\u2014including subjecting people to stereotyping, discrimination, or unfair denial of services. To mitigate these risks, we have opted to not support a general-purpose system in the Face API that purports to infer emotional states, gender, age, smile, facial hair, hair, and makeup. Detection of these attributes will no longer be available to new customers beginning June 21, 2022, and existing customers have until June 30, 2023, to discontinue use of these attributes before they are retired.<\/span>\u201d<\/span><\/p>\nOn emotion detection, facial analysis has historically proven to be much less accurate than simple voice analysis. Voice recognition of emotion has proven quite effective in call center applications, where a customer who sounds very angry can get immediately transferred to a senior supervisor.<\/span><\/p>\nTo a limited extent, that helps make Microsoft\u2019s point that it is the way the data is used that needs to be restricted. In that call center scenario, if the software is wrong and that customer was <\/span>not <\/span><\/i>in fact angry, no harm is done. The supervisor simply completes the call normally. Note: the only common emotion-detection with voice I’ve seen is where the customer is angry at the phonetree and its inability to truly understand simple sentences. The software thinks the customer is angry at the company. A reasonable mistake.<\/span><\/p>\nBut again, if the software is wrong, no harm is done.<\/span><\/p>\nBird made a good point that some use cases can still rely on these AI functions responsibly. \u201c<\/span>Azure Cognitive Services customers can now take advantage of the open-source Fairlearn package and Microsoft\u2019s Fairness Dashboard to measure the fairness of Microsoft\u2019s facial verification algorithms on their own data \u2014 allowing them to identify and address potential fairness issues that could affect different demographic groups before they deploy their technology.\u201d<\/span><\/p>\nBird also said technical issues played a role in some of the inaccuracies. \u201cIn working with customers using our Face service, we also realized some errors that were originally attributed to fairness issues were caused by poor image quality. If the image someone submits is too dark or blurry, the model may not be able to match it correctly. We acknowledge that this poor image quality can be unfairly concentrated among demographic groups.\u201d<\/span><\/p>\nAmong demographic groups? Isn\u2019t that everyone, given that everyone belongs to some demographic group? That sounds like a coy way of saying that non-whites can have poor match functionality. This is why law enforcement\u2019s use of these tools is so problematic. A key question for IT to ask: What are the consequences if the software is wrong? Is the software one of 50 tools being used, or is it being relied upon solely?\u00a0<\/span><\/p>\nMicrosoft said it’s working to fix that issue with a new tool. \u201cThat is why Microsoft is offering customers a new Recognition Quality API that flags problems with lighting, blur, occlusions, or head angle in images submitted for facial verification,\u201d Bird said. \u201cMicrosoft also offers a reference app that provides real-time suggestions to help users capture higher-quality images that are more likely to yield accurate results.\u201d<\/span><\/p>\nIn a <\/span>New York Times <\/span><\/i>interview<\/span><\/a>, Crampton pointed to another issue was with \u201c<\/span>the system\u2019s so-called gender classifier was binary \u2018and that\u2019s not consistent with our values.\u2019\u201d <\/span><\/p>\nIn short, she\u2019s saying while the system not only thinks in terms of just male and female, it couldn\u2019t easily label people who identified in other gender ways. In this case, Microsoft simply opted to stop trying to guess gender, which is likely the right call.<\/span><\/p>\nhttp:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"![](\"https:\/\/images.idgesg.net\/images\/article\/2017\/11\/facial_recognition_system_identification_digital_id_security_scanning_thinkstock_858236252_3x3-100740902-large.3x2.jpg?auto=webp&quality=85,70\"\/)
<\/p>\n
Credit to Author: Evan Schuman| Date: Thu, 07 Jul 2022 03:00:00 -0700<\/strong><\/p>\n\n