{"id":54008,"date":"2016-09-30T11:27:00","date_gmt":"2016-09-30T16:27:00","guid":{"rendered":"https:\/\/content.findlaw-admin.com\/ability-legal\/supreme\/legal-commentary\/the-supreme-court-takes-a-broad-approach-in-interpreting-the-age-discrimination-in-employment-act.html"},"modified":"2016-09-30T11:27:00","modified_gmt":"2016-09-30T16:27:00","slug":"the-supreme-court-takes-a-broad-approach-in-interpreting-the-age-discrimination-in-employment-act","status":"publish","type":"supreme","link":"https:\/\/supreme.findlaw.com\/legal-commentary\/the-supreme-court-takes-a-broad-approach-in-interpreting-the-age-discrimination-in-employment-act.html","title":{"rendered":"The Supreme Court Takes a Broad Approach in Interpreting the Age Discrimination in Employment Act"},"content":{"rendered":"\n<div class=\"wp-container-core-columns-is-layout-9d6595d7  fl-block-columns fl-sectionWithSidebar fl-container fl-flex fl-flex-wrap fl-gap30\">\n    \n    <div class=\"fl-page-articles   fl-block-column fl-section-main fl-section-main-full-width\">\n        <div class=\"yui-g\" id=\"leftcol-module\">\n      <!-- Right Line of Links Section -->\n      <!-- BEGIN PICTURE INSERTION -->\n      <!-- BEGIN TITLE AND AUTHOR INSERTION -->\n      <table>\n        <tr>\n\n          <td width=\"100\" rowspan=\"3\" class=\"wiauthor\"><a href=\"\/legal-commentary\/joanna-grossman-archive\"><img decoding=\"async\" src=\"https://supreme.findlaw.com/static/f/images\/writ\/joanna.grossman.jpg\" border=\"0\"><\/a><\/td>\n          <td class=\"wititle\"><h1>The Supreme Court Takes a Broad Approach in Interpreting the Age Discrimination in Employment Act: <br><span class=\"subtitle\">A Surprising Opinion from a Formalistic Court <\/span><\/h1><\/td>\n        <\/tr>\n        <tr>\n          <td class=\"wiauthor\"><a href=\"\/legal-commentary\/joanna-grossman-archive\" class=\"graybold\"><h2>By JOANNA GROSSMAN<\/h2><\/a><\/td>\n        <\/tr>\n        <tr>\n          <td class=\"widate\">Tuesday, Mar. 04, 2008<\/td>\n\n        <\/tr>\n      <\/table>\n      <span class=\"smalltext\"><p>Last week, the Supreme Court issued an important Age Discrimination in Employment Act (ADEA) opinion, <b><\/b><a href=\"https:\/\/caselaw.findlaw.com\/court\/us-supreme-court\/552\/389.html\" class=\"left-link\" rel=\"noopener\"><i>Federal Express Corp. v. Holowecki<\/i><\/a>. Specifically, the Court considered whether a plaintiff had complied with the necessary procedural formalities required under the ADEA before filing a lawsuit. <\/p>  <p>The opinion is quite significant in that it departs both in tone and substance from recent anti-plaintiff rulings in employment discrimination cases. It is thus a welcome sign of at least a modicum of commitment on the Court&#8217;s part to enforcing the civil rights laws. I <a href=\"\/legal-commentary\/the-supreme-court-considers-a-procedural-roadblock-to-recovery-under-the-age-discrimination-in-employment-act.html\" class=\"left-link\">previously wrote about the case<\/a> when the Court granted review; in this column, I&#8217;ll analyze its opinion.<\/p>  <!-- 300x250 AD -->\n\n<p><b>Federal Age Discrimination Law: The Nuts and Bolts<\/b><\/p>  <p>The federal ADEA was enacted in 1967 &#8211; as a parallel statute to Title VII of the Civil Rights Act of 1964, which prohibits employment discrimination on the basis of race, ethnicity, color, religion, and sex. The ADEA prohibits employers from discriminating against workers who are 40 and over on the basis of their age. <\/p>  <p>The ADEA&#8217;s structure is very similar to Title VII&#8217;s. Among other similarities, both statutes require employees aggrieved by discrimination to first file an administrative complaint with the Equal Employment Opportunity Commission (EEOC) before filing a lawsuit. The EEOC is then supposed to investigate complaints and attempt informal conciliation between the employee and employer. At the end of the day, the EEOC can decide to bring a lawsuit on the employee&#8217;s behalf (which it does in only a small percentage of cases), but most of the time, it steps aside so the employee can pursue her own lawsuit. <\/p>  <p>The administrative and judicial processes do not always work well in tandem. For example, in many cases, the EEOC never investigates or takes any meaningful action, yet, meanwhile, the plaintiff&#8217;s ability to pursue judicial remedies is stalled.  The two processes also are accompanied by confusing and unclear time requirements &#8211; which led to the <i>Holowecki <\/i>case the Court just resolved.<\/p>  <p>Under the ADEA (as under Title VII), an employee must file an EEOC charge within either 180 or 300 days of when the unlawful employment practice occurred. (The difference between the two possible time periods depends on whether he first files a charge with a state fair employment agency that has entered into a work-sharing agreement with the EEOC).  <\/p>  <p>  Under the Supreme Court&#8217;s recently elucidated &#8220;discrete act&#8221; rule, the applicable period begins when an employer takes an adverse act against the employee, such as firing, demotion, or imposing a discriminatory wage. (I have written in previous columns <a href=\"\/legal-commentary\/an-overlooked-problem-with-title-viis-protections-against-discrimination-procedural-obstacles-to-invoking-the-law.html\" class=\"left-link\">such as this one<\/a>, co-authored with Deborah Brake, about the pressures placed on employees by this rule in the Title VII context.)<\/p>  <p>Then, once an employee has filed a &#8220;charge&#8221; with the EEOC, the ADEA imposes a mandatory 60-day waiting period (described at 29 U.S.C. \u00a7 626(d)), during which time the employee <u>cannot<\/u> file a lawsuit. After the EEOC receives a charge, the ADEA mandates that it must notify the employer and initiate conciliation efforts with the employer. The purpose of this period is to allow the EEOC to undertake the investigatory and conciliatory efforts outlined in the statute and regulations.<\/p>  <!-- MIDDLE AD PLACEHOLDER -->\n<p><b>The Dispute in <i>Holowecki<\/i>: A Technical One Over Whether a Plaintiff Filed Her Suit Too Soon<\/b><\/p>  <p><b> <\/b>The question in <i>Holowecki<\/i> is whether the plaintiff filed her lawsuit too soon &#8211; without honoring the 60-day statutory waiting period. The confusion in this case &#8211; and in many similar cases that have reached the federal appellate courts in recent years &#8212; arises from the definition of &#8220;charge&#8221;. <\/p>  <p>The plaintiffs here are current and former FedEx couriers over the age of 40. They filed suit to challenge two new programs implemented by FedEx to make its workforce &#8220;more productive.&#8221; Under these programs, couriers&#8217; compensation and continued employment turn on performance standards like, for example, the number of stops per day made by a courier. The plaintiffs allege that these programs are part of an intentional plan by FedEx to force older couriers out of the company before they reach retirement age. If true, this would be actionable age discrimination by FedEx. But first, it must be determined whether this suit was timely filed; if not, it must be dismissed.<\/p>  <p>In <i>Holowecki<\/i>, the Court considered, in particular, the timeliness of a lawsuit filed plaintiff Patricia Kennedy. Kennedy had filed something with the EEOC called &#8220;Form 283: Intake Questionnaire,&#8221; to which she attached a 6-page sworn affidavit detailing her allegations of discrimination. Then, more than 60 days later, she filed her lawsuit. After that, she filed a more formal charge with the EEOC. <\/p>  <p>FedEx moved to dismiss her lawsuit on the grounds that the Intake Questionnaire and affidavit did not constitute a &#8220;charge alleging unlawful discrimination,&#8221; and thus that the 60-day post-charge waiting period had not even begun to run when Kennedy filed her suit.   <\/p>  <p>Ultimately, however, the Court held, in a 7-2 opinion authored by Justice Kennedy, that the Intake Questionnaire and accompanying affidavit constituted a &#8220;charge&#8221; for purposes of calculating the no-lawsuit waiting period.<\/p>  <p><b>What is a &#8220;Charge&#8221; Under the ADEA? The Relevant Regulations<\/b><\/p>  <p><b> <\/b>Though the ADEA has rules that turn on the timing of a &#8220;charge,&#8221; it never provides a definition. There are, however, two relevant EEOC regulations. The EEOC is empowered to adopt regulations under the ADEA; whether courts defer to those regulations turns upon what the regulations purport to accomplish and how reasonably they do so. The problem, here, however was not that the regulations were unreasonable. It was that they do not provide a clear answer to the question of what constitutes a &#8220;charge&#8221; under the ADEA.<\/p>  <p>One regulation (found at 29 CFR \u00a7 1626.3) defines &#8220;charge&#8221; as &#8220;a statement filed with the [EEOC] by or on behalf of an aggrieved person which alleges that the named prospective defendant has engaged in or is about to engage in actions in violation of the Act.&#8221; A second regulation (found at 29 CFR \u00a7 1626.8(a)) identifies five pieces of information that a &#8220;charge should contain,&#8221; including details like the name and address of the complainant and employer, the number of employees maintained by the employer, and a statement of fact describing the alleged discriminatory acts. And a third regulation (found at 29 CFR 1626.6) states that a &#8220;charge&#8221; is &#8220;sufficient&#8221; if it is &#8220;in writing and name[s] the prospective respondent and . . . generally allege[s] the discriminatory act(s).&#8221;<\/p>  <p><b>The Three Possible Rules the Supreme Court Considered Imposing<\/b><b> <\/b><\/p>  <p>Considering these three regulations together, along with the purpose of the charge-filing and waiting period requirements, the Court had to decide whether an Intake Questionnaire alone, or in conjunction with an affidavit detailing the alleged discrimination, could constitute a &#8220;charge&#8221;. <\/p>  <p>Three possible rules were proposed to the Court. First, FedEx argued in its brief that an Intake Questionnaire cannot constitute a &#8220;charge&#8221; unless the EEOC acts upon it. Second, some appellate courts had ruled in similar cases that an Intake Questionnaire could constitute a charge as long as it made clear the complainant&#8217;s intent to &#8220;activate the EEOC&#8217;s enforcement processes.&#8221; Finally, Patricia Kennedy argued that all completed Intake Questionnaires constitute charges.<\/p>  <p>The Court adopted a variation of the middle-of-the-road position the appellate courts had chosen, affirming the ruling of the court of appeals in this case. Not all documents that include the name of the employer and a description of the acts are sufficient, the Court said, as one of the regulations might have suggested. On the other hand, the Court made clear that not all charges need to be letter-perfect. Ultimately, the Court essentially adopted the standard advocated by the EEOC (put forward in this litigation by the Solicitor General as amicus curiae): <\/p>  <p>&#8220;in addition to the information required by the regulations, <i>i.e.,<\/i> an allegation and the name of the charged party, if a filing is to be deemed a charge it must be reasonably construed as a request for the agency to take remedial action to protect the employee&#8217;s rights or otherwise settle a dispute between the employer and the employee.&#8221;<\/p>  <p>The emphasis is thus not on the particular form the documents take, but on whether they serve the purpose intended by the statutory requirement: to give the EEOC the <u>opportunity<\/u> to notify the charged party (that is, the employer) and initiate conciliation between the parties. Whether the EEOC has the time, resources, or inclination to use that opportunity should not be held against the plaintiff, as the standard urged by FedEx would have done. As the Court concluded, it &#8220;would be illogical and impractical to make the definition of a charge dependent upon a condition subsequent over which the parties have no control.&#8221;<\/p>  <p>Applying its standard to the case at hand, the Court concluded that Kennedy&#8217;s questionnaire and affidavit were sufficient to constitute a &#8220;charge&#8221;. Among other points in her favor were the detailed nature of the allegations provided in the affidavit, and a request at the end to &#8220;[p]lease force Federal Express to end their age discrimination plan so we can finish out our careers absent the unfairness and hostile work environment created&#8221; by the new policies. A reasonable observer, the Court concluded, would understand these documents as a request for EEOC action. Thus, the documents constituted a &#8220;charge&#8221;; Kennedy&#8217;s filing them with the EEOC started the 60-day clock ticking; and she was timely in filing her lawsuit after that period had expired. <\/p>  <p><b>The Practical Meaning of the Court&#8217;s New Standard<\/b><\/p>  <p>What will the Court&#8217;s new standard mean in practice, for employees seeking to preserve their right to sue? <\/p>  <p>First, it is important to recall the Court contemplates under the standard it adopted that a variety of different documents might satisfy the charge-filing requirement, rather than just the single EEOC form designated for that purpose. Thus, this standard will avoid unfairly penalizing laypeople who do their best to navigate the system without a lawyer, as long as they get their message across to the EEOC. It accordingly comports with other areas of law where <i>pro se<\/i> litigants (that is, parties representing themselves) are held to lower pleading standards in pursuing claims. <\/p>  <p>But, still, not everything will qualify: More than half of the employees who contact the EEOC do not ultimately file a &#8220;charge&#8221;; they seek information or assistance of the agency, but never formalize their grievance. The Court thus worried that Kennedy&#8217;s proposed standard &#8211; that all Intake Questionnaires are &#8220;charges&#8221; &#8211; might actually be detrimental to employees, who might avoid seeking assistance from the EEOC because any information would trigger the EEOC&#8217;s mandatory duty to notify the employer and seek conciliation, and thus &#8220;out&#8221; the employee as having raised an issue regarding the employer. <\/p>  <p>Second, and also importantly, the new test does not turn on whether the employee subjectively intended to trigger EEOC action. All that is required is that the documents must make clear to a reasonable observer that the complainant seeks EEOC enforcement. Although this may also open up the possibility that a few employees will inadvertently &#8220;out&#8221; themselves, it avoids the problem of having to assess employee testimony about what was intended.  The court can instead simply look to the document the employee submitted.<\/p>   <p><b>Why This Decision Goes in the Right Direction<\/b> <\/p>  <p>Beyond its effect on the procedures for pursuing age discrimination claims, this opinion is noteworthy for two other reasons. <\/p>  <p>First, the Court goes to great lengths to defer to the EEOC&#8217;s practice and position on this issue, even though the regulations the Commission drafted are admittedly ambiguous and incomplete. This is definitely a good thing: The Court surely should be showing the agency charged with implementing the statute this kind of deference. In prior cases, however, including <a href=\"https:\/\/caselaw.findlaw.com\/court\/us-supreme-court\/550\/618.html\" class=\"left-link\" rel=\"noopener\">the recent ruling in <i>Ledbetter<\/i><\/a>, which I discussed in <a href=\"\/legal-commentary\/the-supreme-court-slams-the-door-on-pay-discrimination-claims-the-ruling-in-ledbetter-v-goodyear-tire-rubber-co.html\" class=\"left-link\">a prior column co-authored with Deborah Brake<\/a>, the Court has demonstrated complete and utter disregard for the EEOC&#8217;s interpretation of anti-discrimination laws.<\/p>  <p>Second, the Court openly acknowledges an important reality of federal anti-discrimination laws: These laws set up a &#8220;remedial scheme in which laypersons, rather than lawyers, are expected to initiate the process.&#8221; For this reason, an overly formalistic approach to procedural requirements can effectively deprive many employees of their substantive rights.  Justice Kennedy acknowledged this risk in <i>Holowecki<\/i>, warning that the &#8220;system must be accessible to individuals who have no detailed knowledge of the relevant statutory mechanisms and agency processes.&#8221; Given recent cases in which the Court has shown little regard for this fact, its newfound awareness, as represented by the laudable <i>Holowecki <\/i>decision, is a welcome development. <\/p>\n\n\n<\/span>\n\n\n\n<hr size=\"1\">\n<p class=\"authorfoot\">\n\n<!-- BEGIN AUTHORS FOOTNOTE -->\n<a name=\"bio\"><\/a>\nJoanna Grossman, a FindLaw columnist, is a professor of law at Hofstra University. Her columns on family law, trusts and estates, and discrimination, including sex discrimination and sexual harassment, may be found in the archive of her columns on this site. \n<br><br>\n\n<\/p>\n    <\/div><div class=\"was-this-helpful\">\n    <div\n            class=\"was-this-helpful__question-container\"\n            aria-labelledby=\"was-this-helpful__question\"\n            role=\"group\"\n    >\n        <span\n                id=\"was-this-helpful__question\"\n                class=\"was-this-helpful__question fl-text-lg-bold\"\n        >Was this helpful?<\/span>\n        <button\n                class=\"was-this-helpful__button fl-text-sm\"\n                aria-label=\"Yes\"\n                value=\"yes\"\n        >\n            <span class=\"was-this-helpful__button-text fl-text-bold\">Yes<\/span>\n            <i class=\"was-this-helpful__button-icon\">\n                <svg width=\"22\" height=\"22\" viewBox=\"0 0 22 22\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <g id=\"thumbs-up\" clip-path=\"url(#clip0_604_3418)\">\n                        <path id=\"Vector\"\n                              d=\"M6 21H3C2.46957 21 1.96086 20.7893 1.58579 20.4142C1.21071 20.0391 1 19.5304 1 19V12C1 11.4696 1.21071 10.9609 1.58579 10.5858C1.96086 10.2107 2.46957 10 3 10H6M13 8V4C13 3.20435 12.6839 2.44129 12.1213 1.87868C11.5587 1.31607 10.7956 1 10 1L6 10V21H17.28C17.7623 21.0055 18.2304 20.8364 18.5979 20.524C18.9654 20.2116 19.2077 19.7769 19.28 19.3L20.66 10.3C20.7035 10.0134 20.6842 9.72068 20.6033 9.44225C20.5225 9.16382 20.3821 8.90629 20.1919 8.68751C20.0016 8.46873 19.7661 8.29393 19.5016 8.17522C19.2371 8.0565 18.9499 7.99672 18.66 8H13Z\"\n                              stroke=\"#666666\" stroke-width=\"2\" stroke-linecap=\"round\"\n                              stroke-linejoin=\"round\"><\/path>\n                    <\/g>\n                    <defs>\n                        <clipPath id=\"clip0_604_3418\">\n                            <rect width=\"22\" height=\"22\" fill=\"white\"><\/rect>\n                        <\/clipPath>\n                    <\/defs>\n                <\/svg>\n            <\/i>\n        <\/button>\n        <button\n                class=\"was-this-helpful__button fl-text-sm\"\n                aria-label=\"No\"\n                value=\"no\"\n        >\n            <span class=\"was-this-helpful__button-text fl-text-bold\">No<\/span>\n            <i class=\"was-this-helpful__button-icon\">\n                <svg width=\"22\" height=\"22\" viewBox=\"0 0 22 22\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n                    <g id=\"thumbs-down\" clip-path=\"url(#clip0_604_3423)\">\n                        <path id=\"Vector\"\n                              d=\"M16 0.999995H18.67C19.236 0.989986 19.7859 1.18813 20.2154 1.55681C20.645 1.9255 20.9242 2.43905 21 3V10C20.9242 10.5609 20.645 11.0745 20.2154 11.4432C19.7859 11.8119 19.236 12.01 18.67 12H16M9.00003 14V18C9.00003 18.7956 9.3161 19.5587 9.87871 20.1213C10.4413 20.6839 11.2044 21 12 21L16 12V0.999995H4.72003C4.2377 0.994543 3.76965 1.16359 3.40212 1.47599C3.0346 1.78839 2.79235 2.22309 2.72003 2.7L1.34003 11.7C1.29652 11.9866 1.31586 12.2793 1.39669 12.5577C1.47753 12.8362 1.61793 13.0937 1.80817 13.3125C1.99842 13.5313 2.23395 13.7061 2.49846 13.8248C2.76297 13.9435 3.05012 14.0033 3.34003 14H9.00003Z\"\n                              stroke=\"#666666\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"\/>\n                    <\/g>\n                    <defs>\n                        <clipPath id=\"clip0_604_3423\">\n                            <rect width=\"22\" height=\"22\" fill=\"white\"\/>\n                        <\/clipPath>\n                    <\/defs>\n                <\/svg>\n            <\/i>\n        <\/button>\n    <\/div>\n    <span class=\"was-this-helpful__taken-action fl-text-sm-bold\"><\/span>\n    <div class=\"was-this-helpful__feedback-container\">\n        <div class=\"was-this-helpful__choose-option-message\" role=\"status\">\n            <p class=\"was-this-helpful__choose-option-message-text\"><\/p>\n        <\/div>\n        <form class=\"was-this-helpful__feedback-form\">\n            <div class=\"was-this-helpful__feedback was-this-helpful__feedback--positive\">\n                <fieldset>\n                    <legend class=\"was-this-helpful__feedback-form-title\" tabindex=\"0\">Why was this helpful?<\/legend>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--understandable\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Easy to understand\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--understandable\"\n                        >Easy to understand<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--solved-problem\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Solved my problem\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--solved-problem\"\n                        >Solved my problem<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--other\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"positive-feedback\"\n                                value=\"Other\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--other\"\n                        >Other<\/label>\n                    <\/div>\n                <\/fieldset>\n            <\/div>\n            <div class=\"was-this-helpful__feedback was-this-helpful__feedback--negative\">\n                <fieldset>\n                    <legend class=\"was-this-helpful__feedback-form-title\" tabindex=\"0\">Why was this not helpful?<\/legend>\n                    <div class=\"was-this-helpful__choose-option-message\" role=\"status\">\n                        <p class=\"was-this-helpful__choose-option-message-text\"><\/p>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--missing-info\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Missing Information\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--missing-info\"\n                        >Missing the information I need<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--complicated\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Too complicated\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--complicated\"\n                        >Too complicated \/ too many steps<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--dated\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Out of date\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--dated\"\n                        >Out of date<\/label>\n                    <\/div>\n                    <div class=\"fl-radio-button-field fl-flex was-this-helpful__feedback-form-title\">\n                        <input\n                                id=\"was-this-helpful__radio-button--negative-other\"\n                                class=\"fl-radio-button-field-input\"\n                                type=\"radio\"\n                                name=\"negative-feedback\"\n                                value=\"Other\"\n                        >\n                        <label\n                                class=\"fl-radio-button-field-label fl-text-sm was-this-helpful__radio-label\"\n                                for=\"was-this-helpful__radio-button--negative-other\"\n                        >Other<\/label>\n                    <\/div>\n                <\/fieldset>\n            <\/div>\n            <div class=\"was-this-helpful__form-buttons-container\">\n                <button\n                    class=\"was-this-helpful__feedback-button was-this-helpful__feedback-button--positive at-feedback-submit fl-button secondary\"\n                    type=\"submit\"\n                >\n                    <span class=\"fl-button-content\">Submit<\/span>\n                    <i\n                        class=\"fa fa-angle-right medium\"\n                        aria-hidden=\"true\"\n                    ><\/i>\n                <\/button>\n                <button\n                    class=\"was-this-helpful__feedback-button was-this-helpful__feedback-button--cancel fl-button primary disabled\"\n                    type=\"reset\"\n                >\n                    <span class=\"fl-button-content\">Cancel<\/span>\n                    <i\n                        class=\"fa fa-times-circle medium\"\n                        aria-hidden=\"true\"\n                    ><\/i>\n                <\/button>\n            <\/div>\n        <\/form>\n    <\/div>\n    <div class=\"was-this-helpful__thank-you-message\" role=\"status\">\n        <i class=\"was-this-helpful__thank-you-message-icon fa fa-check\"><\/i>\n        <p class=\"was-this-helpful__thank-you-message-text\" aria-live=\"polite\"><\/p>\n    <\/div>\n<\/div>\n\n\n    <\/div>\n    \n    <div class=\"fl-block-column fl-section-sidebar\">\n        \n    <\/div>\n<\/div>","protected":false},"parent":49876,"menu_order":0,"template":"app\/Http\/Controllers\/Templates\/ArticlePageController.php","meta":{"_acf_changed":false,"_stopmodifiedupdate":false,"_modified_date":"","_cloudinary_featured_overwrite":false},"class_list":["post-54008","supreme","type-supreme","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme\/54008","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme"}],"about":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/types\/supreme"}],"up":[{"embeddable":true,"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/supreme\/49876"}],"wp:attachment":[{"href":"https:\/\/supreme.findlaw.com\/legal-api\/wp-json\/wp\/v2\/media?parent=54008"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}